Audio Capture on Mobile Client Devices

ABSTRACT

Audio capture techniques on mobile client devices are described. In one or more implementations, techniques are described for leveraging availability of audio data captured by other devices involving a video scene that have an increased proximity to the video scene. Video data is obtained by one or more computing devices from a first client device associated with a first user, the video data captured by the first client device of a video scene. Audio data is obtained by the one or more computing devices from a second client device associated with a second user, the second user included in the video data of the video scene. The one or more computing devices ascertain that the audio data is associated with the video data. The association is exposed by the one or more computing device of the audio data to the video data as indicating availability of at least a portion of the audio data as a replacement to audio data captured by the first client device as part of the video data.

BACKGROUND

The prevalence of video capture continues to follow an increase inavailability of client devices that include this functionality, such asmobile phones, tablets, and so on. However, in conventional techniquesthe capture of images as part of the video is given greater prioritythan the capture of corresponding audio. For example, cameras includedin these mobile client devices continue to increase to support increasedrichness and features.

On the other hand, audio captured by the mobile client devices islimited by an ability of microphones to capture desired audio that is tobe output along with the images. This may be due to a variety ofdifferent factors, such as optimization of the microphones for phoneusage and thus “up close” capture of audio, a distance between themobile client device and a source of the audio, and so forth.Consequently, limitations of the audio may adversely affect a user'sexperience with the output of the images as part of the video, therebydecreasing the overall experience as a whole and thus may cause users toforgo the experience in instances in which the audio is likely to becorrupted.

SUMMARY

Audio capture techniques on mobile client devices are described. In oneor more implementations, techniques are described for leveragingavailability of audio data captured by other devices involving a videoscene that have an increased proximity to the video scene. Video data isobtained by one or more computing devices from a first client deviceassociated with a first user, the video data captured by the firstclient device of a video scene. Audio data is obtained by the one ormore computing devices from a second client device associated with asecond user, the second user included in the video data of the videoscene. The one or more computing devices ascertain that the audio datais associated with the video data. The association is exposed by the oneor more computing device of the audio data to the video data asindicating availability of at least a portion of the audio data as areplacement to audio data captured by the first client device as part ofthe video data.

In one or more implementations, techniques are described for replacingaudio data for playback along with video data. A user interface isdisplayed by one or more computing devices. The user interface includesrepresentations of video data and first audio data captured by a firstclient device of a video scene and second audio data captured by asecond client device of the video scene. One or more inputs are receivedby the one or more computing devices to replace at least a portion ofthe first audio data with a corresponding portion of the second audiodata. A file is generated by the one or more computing devices that isconfigured for playback that includes the portion of the second audiodata configured for output along with the video data.

In one or more implementations, a system includes one or more computingdevices implemented partially in hardware, the one or more computingdevices configured to perform operations. The operations includesobtaining video data and first audio data from a first client deviceassociated with a first user, the video data and the first audio datacaptured by the first client device of a video scene and obtainingsecond audio data from a second client device associated with a seconduser, the second client device closer to the video scene than the firstclient device. One or more inputs are received to replace at least aportion of the first audio data with a corresponding portion of thesecond audio data and a file is generated that is configured forplayback that includes the portion of the second audio data configuredfor output along with the video data.

This Summary introduces a selection of concepts in a simplified formthat are further described below in the Detailed Description. As such,this Summary is not intended to identify essential features of theclaimed subject matter, nor is it intended to be used as an aid indetermining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different instances in thedescription and the figures may indicate similar or identical items.Entities represented in the figures may be indicative of one or moreentities and thus reference may be made interchangeably to single orplural forms of the entities in the discussion.

FIG. 1 is an illustration of an environment in an example implementationthat is operable to employ audio and video capture techniques describedherein.

FIG. 2 depicts a system in an example implementation in which video andaudio data are associated, one to another, to support audio replacementediting operations.

FIG. 3 depicts an example implementation of an editing technique usableto replace at least a portion of audio data using the associated audioand video data as described in relation to FIG. 2.

FIG. 4 is a flow diagram depicting a procedure in an exampleimplementation in which techniques are described for leveragingavailability of audio data captured by other devices involving a videoscene that have an increased proximity to the video scene.

FIG. 5 is a flow diagram depicting a procedure in an exampleimplementation in which techniques are described for replacing audiodata for playback along with video data.

FIG. 6 illustrates an example system including various components of anexample device that can be implemented as any type of computing deviceas described and/or utilize with reference to FIGS. 1-5 to implementembodiments of the techniques described herein.

DETAILED DESCRIPTION

Overview

The amount of video captured by users has increased due to inclusion offunctionality to capture video on mobile client devices such as mobilephones, tablets, and so on. Consequently, these devices are typicallyreadily available to users and this availability has caused the increasein video capture. However, conventional video capture techniques placelittle emphasis on the audio that accompanies the video, which may bedue to limitations of microphones included with the device. Conventionaltechniques to overcome these limitations involve use of dedicatedhardware, which could be expensive and not readily available to a user.

Audio capture techniques involving mobile client devices is described.In one or more implementations, these techniques leverage hardware thatis readily available to users to improve audio recording that isassociated with images in a video. For example, first and second usersmay download applications from an application store via the Internet. Afirst user may then capture video of the second user in a video sceneusing a first client device associated with the first user (e.g., amobile phone), such as in front of a stadium for a sporting event.

The second user in the example also has a second client device (e.g., amobile phone) on the user's person, such as placed in a pocket of thesecond user. The second client device is used to capture audio data in aproximity of the second user, and thus of the video scene being capturedby the first user. Therefore, the audio captured by the second clientdevice has an increased likelihood of accuracy (e.g., lack of noise)over audio data captured by the first client device through a closerproximity to the second user, such as to capture speech of the seconduser.

The applications may then be used to share the video and audio, e.g.,directly, via the cloud, and so forth. In this way, audio captured bythe second user may be used to replace audio captured by the first useras described to generate a file that includes the video and the replacedaudio. Therefore, mobile devices that are commonly available to usersare leveraged without additional hardware through use of theapplications to increase richness of audio that is configured for outputalong with images in the video. Further discussion of these and otherexamples is described in the following sections and shown incorresponding figures.

In the following discussion, an example environment is first describedthat may employ the techniques described herein. Example procedures arethen described which may be performed in the example environment as wellas other environments. Consequently, performance of the exampleprocedures is not limited to the example environment and the exampleenvironment is not limited to performance of the example procedures.

Example Environment

FIG. 1 is an illustration of an environment 100 in an exampleimplementation that is operable to employ the audio capture techniquesdescribed herein. The illustrated environment 100 includes a serviceprovider 102 and client devices 104, 106 that are communicativelycoupled, one to another, via a network 108.

Computing devices that implement the service provider 102 and the clientdevices 104, 106 may be configured in a variety of ways. For example,computing devices may be configured as a conventional desktop computer,game console, and so forth. Mobile configurations are also contemplated,such as a mobile station, a portable entertainment appliance, a mobilecomputing device having a housing configured in accordance with ahandheld configuration (e.g., a mobile phone or tablet), a wirelessphone, and so forth.

Thus, computing devices may range from full resource devices withsubstantial memory and processor resources (e.g., personal computers,game consoles) to low-resource devices with limited memory and/orprocessing resources (e.g., traditional set-top boxes, hand-held gameconsoles). Additionally, although instances of a single computingdevices are shown, the computing devices may be representative of aplurality of different devices, such as multiple servers utilized by abusiness to perform operations such as by a web service by the serviceprovider 102, a remote control and set-top box combination, and so on.

The service provider 102 may be implemented using any suitable type ofserver that can provide any suitable type of service that can beconsumed online In at least some embodiments, the server or servers canbe configured to operate in a so-called “cloud computing” environment.Cloud computing refers to a computing model that enables ubiquitousnetwork access to a shared and virtualized pool of computingcapabilities. Such computing capabilities can include, by way of exampleand not limitation, network, storage, processing, and memorycapabilities that can be rapidly provisioned. Cloud computing canencompass a variety of cloud providers, as well as severalinfrastructure-as-a-service (Iaas) and platform-as-a-service (Paas)solutions.

Although the network 108 is illustrated as the Internet, the network mayassume a wide variety of configurations. For example, the network 108may include a wide area network (WAN), a local area network (LAN), awireless network, a public telephone network, an intranet, and so on.Further, although a single network 108 is shown, the network 108 may beconfigured to include multiple networks.

The client devices 104, 106 are illustrated as including respectivecontent interaction modules 110, 112, cameras 114, 116, and microphones118, 120. As is readily apparent, the cameras 114, 116 arerepresentative of hardware functionality to capture images that formvideo data 122 and the microphones 118, 120 are representative offunctionality to capture sound as audio data 124, such as music, spokenutterances, environmental sounds, and so forth.

The content interaction modules 110, 112 are representative offunctionality to manage capture, sharing, and editing of the video andaudio data 122, 124, which may be performed directly between the clientdevices 104, 106 and/or utilize an intermediary such as the serviceprovider 102. Content interaction module 110, for instance, may transfervideo (and even audio data) via the network 108 for storage 126 by acontent management module 128. Content interaction module 112 may alsotransfer audio data 124 via the network 108 for storage 126 by thecontent management module 128.

For example, client device 104 is associated with a first user 130 inthe illustration and client device 106 is associated with a second user132. The first user 130 captures video data 122 of a video scene 134that includes the second user 132, e.g., the second user 132 and partsof a surrounding environment of the second user 132. Both the first andsecond users 130, 132 in this example have obtained applications thatinclude the content interaction module 110, 112 (e.g., online from anapplication store) that support association of the data captured by thedevices.

Accordingly, the first user 130 may capture video data 122 of the videoscene 134 that includes the second user 132. The second user 132,through use of the client device 112, captures audio data 124 of thevideo scene 134 also, e.g., by initiating the application and placingthe client device 106 on the user's person, e.g., in a pocket of theuser. In this way, the audio data 124 captured by the client device 106may have less noise than audio data captured by client device 104through a closer proximity to the second user 132, such as to capturespoken utterances of the user.

The content management module 128 of the service provider 102 may thenexpose a variety of different functionality relating to this data. Thismay include managing an association of the audio data 124 with the videodata 122, support editing functionality such as to replace audio datacaptured by client device 104 with audio data captured by client device106, and so forth. Although this functionality is described in relationto the content management module 128 in the following, thisfunctionality may also be implemented locally by the content interactionmodules 110, 112 of the client devices 104, 106, in whole or in part.

Generally, any of the functions described herein can be implementedusing software, firmware, hardware (e.g., fixed logic circuitry), manualprocessing, or a combination of these implementations. The terms“module,” “functionality,” and “logic” as used herein generallyrepresent software, firmware, hardware, or a combination thereof. In thecase of a software implementation, the module, functionality, or logicrepresents program code that performs specified tasks when executed on aprocessor (e.g., CPU or CPUs). The program code can be stored in one ormore computer readable storage media. The features of thevolatility-based classifier are platform-independent, meaning that thetechniques may be implemented on a variety of commercial computingplatforms having a variety of processors.

FIG. 2 depicts a system 200 in an example implementation in which videoand audio data are associated, one to another, to support of audioreplacement editing operations. The system 200 is illustrated as usingfirst and second stages 202, 204. At the first stage 202, video data andaudio data 206, 208 captured by client device 104 are transmitted via anetwork 108 into storage 126 of the service provider 102. A user, forinstance, may initiate execution of an application on a mobile phone andcapture video and audio data 206, 208, which may be streamedautomatically, uploaded responsive to a user selection in a graphicaluser interface, and so forth.

Client device 106 also transmits audio data 210 for storage 126 by theservice provider 102, which may include initiation of a companionapplication and automatic transfer, transfer responsive to userselection, and so on. As previously described in relation to FIG. 2, theclient device 106 may be kept on a person of the second user 132 that isbeing filed by the first user 130.

At the second stage 204, the content management module 128 isillustrated as including a content association module 212. The contentassociation module 212 is representative of functionality to create acontent association 214 between the video and audio data 206, 208captured by client device 104 with audio data 210 captured by clientdevice 106.

The content association 214 may be defined and thus realized in avariety of ways. Continuing with the previous example of applicationusage, these applications may have corresponding user accounts that aremanaged by the service provider 102. As part of this management, thecontent management module 128 may support permissions 216 to grantaccess to the video and/or audio data. The first user 130 of FIG. 1, forinstance, may grant permission to the second user 132 to gain access tothe video and audio data 206, 208. The first user 130 may also gainaccess to the audio data 210 of the second user 132, e.g., throughacceptance of a request for such access, by accepting the request fromthe first user 130, and so forth.

In another example, time 218 and/or location 220 of the video 206 andaudio data 208, 210 may be used as a basis by the content associationmodule 212 to make the content association 214. The video data 206, forinstance, may have associated metadata that describes a time 218 and/orlocation 220 at which the video and audio data 206, 208 are captured.This may be matched with metadata of the audio data 210 to determine thecontent association 214.

In a first example, association with a particular event 222 may be usedby the content association module 212. This association may either beexplicitly or implicitly determined by the content association module212. In the explicit example, metadata specifies a particular event,which may be included automatically by the client devices 104, 106 ormanually input by a user. This metadata may specify a particularsporting event, concert, birthday party, class reunion, wedding, and soforth.

The event 222 may also be determined implicitly by the contentassociation module 212. For example, the time 218 and location 220 maybe matched with a table of events occurring at specified times andlocations. The content association module 212 may then make the contentassociation 214 based on this determination. In one or moreimplementations, users may be given an option to share video and/oraudio data captured at these events with other users that are notspecifically known to the user, such as to share concert footage andaudio and so forth with other attendees of the concert.

Other 224 content associations 214 may also be determined automaticallyand without user intervention by the content association module 212,such as to identify video and/or audio data 206, 208 of a similarsubject matter (e.g., sunsets), characteristics (e.g., night), and soforth. The content association 214 may be leveraged in a variety ofways, such as to support replacement functionality, an example of whichis described in the following and shown in a corresponding figure.

FIG. 3 depicts an example implementation 300 of an editing techniqueusable to replace at least a portion of audio data using the audio andvideo data captured as described in relation to FIG. 2. In this example,storage 302 of the client device 104 is illustrated as maintaining thevideo data 206 and audio data 208, 210 as part of the contentassociation 214 from the previous figure. The content interaction module110 further includes a content editing module 304 that is configured tosupport techniques the edit the video and audio data 206, 208, 210 toform a file for playback.

For example, the content editing module 304 is illustrated as causingoutput of a user interface 306 on a display device of the client device104. The user interface 306 includes a representation 308 of the videodata 206 showing a plurality of images (i.e., frames) of the video data206 captured as part of the video by the client device 104. Audio data208 captured along with the video data 206 is represented 310 as atime/frequency waveform that is time aligned with the frames of thevideo data 206.

The user interface 306 also includes a representation 312 of the audiodata 210 captured by client device 106 that is associated with the videoand audio data 206, 208. The representation 312 is also configured as atime/frequency representation that is time aligned with therepresentation 310 of the audio data 208 and the representation 308 ofthe video data 206. A playback window 314 is also included in the userinterface 314 to view a current playback position of the video data 206.

In this example, the content editing module 304 is configured to supportediting such that a whole or part of the audio data 208 associated withthe video data 206 captured by client device 104 may be replaced withaudio data 210 captured by client device 106. As illustrated by therepresentation 312, audio data 210 captured by client device 106 hasless noise and thus is more readily able to recreate speech by thesecond user 132 in the video scene 134 as opposed to noise captured byclient device 104 as shown by representation 310 of audio data 208. Thisis due in this example to placement of the client device 106 at a closerproximity to the second user 132 (e.g., on the user's person) thanclient device 104, although other examples are also contemplated, suchas due to differences in ability of the microphones 118, 120 toaccurately capture audio data.

A user, for instance, may selection portions of the representation 310of audio data 208 to be replaced by corresponding portions of therepresentation 312 of audio data 210 through use of a cursor controldevice, gesture, spoken utterance, and so forth. Once selections anddesired replacements have been completed, the user may initiate anoperation of the content editing module 304 to form a file for playbackthat includes the video data 206 and selection portions of the audiodata 210. In this way, a user may readily replace audio data associatedwith the video data 206 as desired to obtain an optimal playbackexperience by leveraging readily available client devices 104, 106.

Although shown as being performed at the client device 104, it should bereadily apparent that the user interface 306 may be output at the clientdevice 104 but processing performed by the content editing module 304“in the cloud” through interaction with the service provider 102 via thenetwork 108. A variety of other examples are also contemplated, furtherdiscussion of which is included in the following section.

Example Procedures

The following discussion describes audio capture and editing techniquesthat may be implemented utilizing the previously described systems anddevices. Aspects of each of the procedures may be implemented inhardware, firmware, or software, or a combination thereof. Theprocedures are shown as a set of blocks that specify operationsperformed by one or more devices and are not necessarily limited to theorders shown for performing the operations by the respective blocks. Inportions of the following discussion, reference will be made to FIGS.1-3

FIG. 4 depicts a procedure 400 in an example implementation in whichtechniques are described for leveraging availability of audio datacaptured by other devices involving a video scene that have an increasedproximity to the video scene. Video data is obtained by one or morecomputing devices from a first client device associated with a firstuser, the video data captured by the first client device of a videoscene (block 402). The service provider 102, for example, may obtainvideo and audio data 206, 208 via the network 108 from client device104.

Audio data is obtained by the one or more computing devices from asecond client device associated with a second user, and the second useris included in the video data of the video scene (block 404). Continuingwith the previous example, the service provider 102 may also obtainaudio data 210 from client device 106 via the network 108.

The one or more computing devices ascertain that the audio data isassociated with the video data (block 406). The association may bedefined in a variety of ways, such as via a permission 216, time 218,location 220, event 222, or other 224 association indicating that audiodata 210 is usable to replace at least a portion of audio data 208 thatis captured along with the video data 206 by client device 104.

The association is exposed by the one or more computing device of theaudio data to the video data as indicating availability of at least aportion of the audio data as a replacement to audio data captured by thefirst client device as part of the video data (block 408). This mayinclude indicating to a user of client device 104 that audio data 210 isavailable via the service provider 102 for download, output in a userinterface 306 configured to support editing and generation of a file forplayback, and so forth. In this way, availability is leveraged of audiodata captured by other devices involving a video scene that have anincreased proximity to the video scene

FIG. 5 depicts a procedure 500 in an example implementation in whichtechniques are described for replacing audio data for playback alongwith video data. A user interface is displayed by one or more computingdevices. The user interface includes representations of video data andfirst audio data captured by a first client device of a video scene andsecond audio data captured by a second client device of the video scene(block 502). User interface 306, for instance, includes a representation308 of images of video data 206 and a representation 310 of audio data208 captured by client device 104. The user interface 306 also includesa representation 312 of audio data 210 captured by client device 106.

One or more inputs are received by the one or more computing devices toreplace at least a portion of the first audio data with a correspondingportion of the second audio data (block 504). The inputs, for instance,may select a range of time in the time/frequency representation 312 thatis to be output along with the video data 308.

A file is generated by the one or more computing devices that isconfigured for playback that includes the portion of the second audiodata configured for output along with the video data (block 506). Thecontent editing module 304 may then employ a codec to form the file forplayback that includes the video data 206 and the audio data 210. Avariety of other examples are also contemplated as described above.

Example System and Device

FIG. 6 illustrates an example system generally at 600 that includes anexample computing device 602 that is representative of one or morecomputing systems and/or devices that may implement the varioustechniques described herein. This is illustrated through inclusion ofthe content interaction module 110 and content management module 128.The computing device 602 may be, for example, a server of a serviceprovider, a device associated with a client (e.g., a client device), anon-chip system, and/or any other suitable computing device or computingsystem.

The example computing device 602 as illustrated includes a processingsystem 604, one or more computer-readable media 606, and one or more I/Ointerface 608 that are communicatively coupled, one to another. Althoughnot shown, the computing device 602 may further include a system bus orother data and command transfer system that couples the variouscomponents, one to another. A system bus can include any one orcombination of different bus structures, such as a memory bus or memorycontroller, a peripheral bus, a universal serial bus, and/or a processoror local bus that utilizes any of a variety of bus architectures. Avariety of other examples are also contemplated, such as control anddata lines.

The processing system 604 is representative of functionality to performone or more operations using hardware. Accordingly, the processingsystem 604 is illustrated as including hardware element 610 that may beconfigured as processors, functional blocks, and so forth. This mayinclude implementation in hardware as an application specific integratedcircuit or other logic device formed using one or more semiconductors.The hardware elements 610 are not limited by the materials from whichthey are formed or the processing mechanisms employed therein. Forexample, processors may be comprised of semiconductor(s) and/ortransistors (e.g., electronic integrated circuits (ICs)). In such acontext, processor-executable instructions may beelectronically-executable instructions.

The computer-readable storage media 606 is illustrated as includingmemory/storage 612. The memory/storage 612 represents memory/storagecapacity associated with one or more computer-readable media. Thememory/storage component 612 may include volatile media (such as randomaccess memory (RAM)) and/or nonvolatile media (such as read only memory(ROM), Flash memory, optical disks, magnetic disks, and so forth). Thememory/storage component 612 may include fixed media (e.g., RAM, ROM, afixed hard drive, and so on) as well as removable media (e.g., Flashmemory, a removable hard drive, an optical disc, and so forth). Thecomputer-readable media 606 may be configured in a variety of other waysas further described below.

Input/output interface(s) 608 are representative of functionality toallow a user to enter commands and information to computing device 602,and also allow information to be presented to the user and/or othercomponents or devices using various input/output devices. Examples ofinput devices include a keyboard, a cursor control device (e.g., amouse), a microphone, a scanner, touch functionality (e.g., capacitiveor other sensors that are configured to detect physical touch), a camera(e.g., which may employ visible or non-visible wavelengths such asinfrared frequencies to recognize movement as gestures that do notinvolve touch), and so forth. Examples of output devices include adisplay device (e.g., a monitor or projector), speakers, a printer, anetwork card, tactile-response device, and so forth. Thus, the computingdevice 602 may be configured in a variety of ways as further describedbelow to support user interaction.

Various techniques may be described herein in the general context ofsoftware, hardware elements, or program modules. Generally, such modulesinclude routines, programs, objects, elements, components, datastructures, and so forth that perform particular tasks or implementparticular abstract data types. The terms “module,” “functionality,” and“component” as used herein generally represent software, firmware,hardware, or a combination thereof. The features of the techniquesdescribed herein are platform-independent, meaning that the techniquesmay be implemented on a variety of commercial computing platforms havinga variety of processors.

An implementation of the described modules and techniques may be storedon or transmitted across some form of computer-readable media. Thecomputer-readable media may include a variety of media that may beaccessed by the computing device 602. By way of example, and notlimitation, computer-readable media may include “computer-readablestorage media” and “computer-readable signal media.”

“Computer-readable storage media” may refer to media and/or devices thatenable persistent and/or non-transitory storage of information incontrast to mere signal transmission, carrier waves, or signals per se.Thus, computer-readable storage media refers to non-signal bearingmedia. The computer-readable storage media includes hardware such asvolatile and non-volatile, removable and non-removable media and/orstorage devices implemented in a method or technology suitable forstorage of information such as computer readable instructions, datastructures, program modules, logic elements/circuits, or other data.Examples of computer-readable storage media may include, but are notlimited to, RAM, ROM, EEPROM, flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical storage, harddisks, magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or other storage device, tangible media, orarticle of manufacture suitable to store the desired information andwhich may be accessed by a computer.

“Computer-readable signal media” may refer to a signal-bearing mediumthat is configured to transmit instructions to the hardware of thecomputing device 602, such as via a network. Signal media typically mayembody computer readable instructions, data structures, program modules,or other data in a modulated data signal, such as carrier waves, datasignals, or other transport mechanism. Signal media also include anyinformation delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media include wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared, and other wireless media.

As previously described, hardware elements 610 and computer-readablemedia 606 are representative of modules, programmable device logicand/or fixed device logic implemented in a hardware form that may beemployed in some embodiments to implement at least some aspects of thetechniques described herein, such as to perform one or moreinstructions. Hardware may include components of an integrated circuitor on-chip system, an application-specific integrated circuit (ASIC), afield-programmable gate array (FPGA), a complex programmable logicdevice (CPLD), and other implementations in silicon or other hardware.In this context, hardware may operate as a processing device thatperforms program tasks defined by instructions and/or logic embodied bythe hardware as well as a hardware utilized to store instructions forexecution, e.g., the computer-readable storage media describedpreviously.

Combinations of the foregoing may also be employed to implement varioustechniques described herein. Accordingly, software, hardware, orexecutable modules may be implemented as one or more instructions and/orlogic embodied on some form of computer-readable storage media and/or byone or more hardware elements 610. The computing device 602 may beconfigured to implement particular instructions and/or functionscorresponding to the software and/or hardware modules. Accordingly,implementation of a module that is executable by the computing device602 as software may be achieved at least partially in hardware, e.g.,through use of computer-readable storage media and/or hardware elements610 of the processing system 604. The instructions and/or functions maybe executable/operable by one or more articles of manufacture (forexample, one or more computing devices 602 and/or processing systems604) to implement techniques, modules, and examples described herein.

The techniques described herein may be supported by variousconfigurations of the computing device 602 and are not limited to thespecific examples of the techniques described herein. This functionalitymay also be implemented all or in part through use of a distributedsystem, such as over a “cloud” 614 via a platform 616 as describedbelow.

The cloud 614 includes and/or is representative of a platform 616 forresources 618. The platform 616 abstracts underlying functionality ofhardware (e.g., servers) and software resources of the cloud 614. Theresources 618 may include applications and/or data that can be utilizedwhile computer processing is executed on servers that are remote fromthe computing device 602. Resources 618 can also include servicesprovided over the Internet and/or through a subscriber network, such asa cellular or Wi-Fi network.

The platform 616 may abstract resources and functions to connect thecomputing device 602 with other computing devices. The platform 616 mayalso serve to abstract scaling of resources to provide a correspondinglevel of scale to encountered demand for the resources 618 that areimplemented via the platform 616. Accordingly, in an interconnecteddevice embodiment, implementation of functionality described herein maybe distributed throughout the system 600. For example, the functionalitymay be implemented in part on the computing device 602 as well as viathe platform 616 that abstracts the functionality of the cloud 614.

CONCLUSION

Although the invention has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the invention defined in the appended claims is not necessarilylimited to the specific features or acts described. Rather, the specificfeatures and acts are disclosed as example forms of implementing theclaimed invention.

What is claimed is:
 1. A method of leveraging availability of audio datacaptured by another device, the method comprising: capturing, by a firstclient device, video data and first audio data of a video scene;determining, by the first client device, that second audio data isassociated with the video data, the second audio data captured by asecond client device; gaining access, by the first client device, to thesecond audio data; receiving, by the first client device, one or moreinputs to replace at least a portion of the first audio data with acorresponding portion of the second audio data; and generating a fileconfigured for playback that includes the corresponding portion of thesecond audio data configured for output along with the video data.
 2. Amethod as described in claim 1, wherein the determining that the secondaudio data is associated with the video data is based in part on a timeand location of capturing the second audio data.
 3. A method asdescribed in claim 2, wherein the time and location of capturing thesecond audio data is determined based on metadata associated with thesecond audio data.
 4. A method as described in claim 3, wherein themetadata specifies a particular event via manual input from a user ofthe second client device.
 5. A method as described in claim 3, whereinthe metadata specifies a particular event included automatically by thesecond client device.
 6. A method as described in claim 3, wherein thedetermining includes a comparison of the metadata with a table of eventsoccurring at specified times and locations.
 7. A method as described inclaim 1, wherein the determining includes receiving, from a serviceprovider, an indication of an association of the second audio data withthe first video data.
 8. A method as described in claim 1, whereingaining access includes accessing the second audio data via a serviceprovider storing the second audio data.
 9. A method as described inclaim 1, wherein the one or more inputs are received via a userinterface of the first client device, the user interface including arepresentation of the video data, the first audio data, and the secondaudio data.
 10. A method as described in claim 1, wherein the generatedfile includes the corresponding portion of the second audio data,another portion of the first audio data, and the video data.
 11. Acomputing device comprising: a processing system; and acomputer-readable storage medium having stored thereon instructions thatimplement a platform of the computing device that, responsive toexecution by the processing system, cause the processor to performoperations comprising: capturing video data and first audio data of avideo scene; ascertaining, via a service provider, that second audiodata is associated with the video data, the second audio data capturedby another computing device; gaining access, via the service provider,to the second audio data; replacing at least a portion of the firstaudio data with a corresponding portion of the second audio data; andgenerating a file configured for playback that includes thecorresponding portion of the second audio data configured for outputalong with the video data.
 12. A computing device as described in claim11, wherein the operations further comprise streaming the captured videodata to the service provider to match the captured video data to thesecond audio data.
 13. A computing device as described in claim 11,wherein the operations further comprise uploading, in response to a userinput, the captured video data to the service provider for matching thecaptured video data with the second audio data.
 14. A computing deviceas described in claim 11, wherein the gaining access comprisesrequesting, from the service provider, access to the second audio data.15. A computing device as described in claim 11, wherein the computingdevice is one of a mobile phone or a tablet computing device.
 16. Acomputing device as described in claim 11, wherein the operationsfurther comprise facilitating the ascertaining and the gaining accessvia a previously downloaded application.
 17. In a digital mediumenvironment to leverage availability of audio data captured by anotherdevice, a system comprising: means for capturing video data and firstaudio data of a video scene, the video data including metadatadescribing one or more of the time or location at which the video datais captured; means for ascertaining, based in part on the metadata ofthe video data, that second audio data is associated with the videodata, the second audio data captured by the other device and includingmetadata describing one or more of a time or location at which thesecond audio data is captured; means for gaining access to the secondaudio data; means for replacing at least a portion of the first audiodata with a corresponding portion of the second audio data.
 18. A systemas described in claim 17, wherein the other device is closer to thevideo scene than the first client device.
 19. A system as described inclaim 17, wherein the association is ascertained based at least in parton matching the metadata of the video data and the metadata of the audiodata.
 20. A system as described in claim 17, wherein one or both of thesystem and the other device includes a mobile phone.